Somatic Neuron
   |
Posted - 2006.01.23 19:18:00 -
[1]
 Originally by: Abdalion
Originally by: Shamis Orzoz
Edited by: Shamis Orzoz on 23/01/2006 16:12:49
I love how the GM's and/or mods ask you to file a bug report when big bugs like this are found. You pay them to provide you with a game, but when there is a problem, YOU have to write up the bug report for them. It seems like they should contact you, or at least read the damn thread.
That being said, I don't care what happens with carriers, fix the lag, fix bizarre stacking of modules acrosss ships that either wasn't intended or poorly thought out, and make POS's work before you add more content.
Hello Mr. Orzoz,
The reason that we mods tell you to file a bug report, is because we can't assist you any other way. We mods must also file bug reports when we notice things and can personally forward relevant information that will assist the appropriate teams in fixing the problem. The people who get these bug reports need them in order to do their job, they can't just read the forums and pick which bugs to look into, as they need the detailed information that the players provide.
Reading a thread is not hard evidence. It is indicative of a problem yes, but without necessary information sent in a proper format, there is no track record of steps taken to outline the problem.
I can't speak for the GM's on this issue, but I can easily assume that they are afflicted with a similar desire to assist the players, but are unable to do so because the players don't follow the best path available, which is to submit a detailed bug report.
Bug Reports Start Here
The problem I see, Abdalion, is that the devs are notoriously lax when it comes to acknowledging bugs. How many dozens of bugs have been reported and confirmed by Devs in the forums, yet the "Known Issues" page is never (or rarely) updated with this information. All known issues should be listed, and a history kept of those known issues so that we can see if those issues are reintroduced (as is often the case with patches) on subsequent patches. In every major software development project I have been involved with, bugs are tracked with issue numbers, and the status is updated as it changes. For instance
BugID: B20060121000004
Status: Fixed on SiSi
Issue Title: Carrier Corp Hangar space bugged
Issue Description: When you place Isotopes in the Corp Hangar, the volume used is listed incorrectly.
Dev Notes: Confirmed this to be an issue. This is a display bug and doesn't have any effect on what can and cannot be put into the Carrier's Corp Hangar. Updated the code to display correctly, and pushed code to SiSi for testing.
QA Notes: Verified the issue is fixed on SiSi. Code is approved for next patch.
---------- |